Methods, systems and computer readable media for modifying parameters of a configuration file

ABSTRACT

Disclosed is a method of configuring a medical device through utilization of a computing device that includes a user interface, a processor and memory. The method includes the steps of determining whether a configuration file contains a focal modified parameter, displaying the focal modified parameter, prompting a manual re-entry of the displayed focal modified parameter, receiving through the user interface the manual re-entry of the displayed focal modified parameter, and utilizing the processor to automatically determine whether the manual re-entry of the displayed focal modified parameter matches the displayed focal modified parameter.

TECHNICAL FIELD

The invention relates to methods, systems and computer readable mediafor modifying parameters of a configuration file that is written to amedical device.

BACKGROUND

Diabetes is a disease in which the body does not produce or properly useinsulin. To effectively manage the disease, diabetics must closelymonitor and manage their blood glucose levels through exercise, diet andmedication. In some situations, diabetics may also rely on insulindelivery to control the effects of the disease. Traditionally, insulinwas injected with a syringe multiple times during the day. However,developments in technology currently allow for the delivery of insulinfrom a reservoir via a catheter with a percutaneous needle or cannulaplaced in the subcutaneous tissue. A programmable insulin pump controlsthe delivery of insulin according to a individualized configuration file(i.e., a set of delivery parameters). For example, a small amount ofinsulin, or a basal rate, may be continually delivered to a user. Thebasal rate keeps the user's blood glucose levels in the desired rangebetween meals and during sleep. When food is eaten, the user may furthercontrol the pump to deliver an additional bolus (i.e., set dose) ofinsulin to counteract the effect that the ingested food has on theuser's blood glucose levels.

However, errors in setting or modifying the pump configuration fileparameters (e.g., too large or small of a basal rate and/or bolusamount, etc.) may lead to serious health consequences for the user.Accordingly, error-reducing methods, systems and computer readable mediautilized in the setting and/or modification of the parameters of a pumpconfiguration file (or a configuration file for any other medicaldevice) are of continued interest.

SUMMARY

One embodiment of a method of configuring a medical device throughutilization of a computing device that includes a user interface, aprocessor and memory, includes the steps of: receiving in memory aconfiguration file with one or more modified parameters; establishingcommunication between the medical device and the computing device;utilizing the processor to automatically read the configuration filefrom memory, determine whether the configuration file contains modifiedparameters that are focal, display the modified parameters on the userinterface, and prompt a confirmation of the displayed modifiedparameters; receiving through the user interface the confirmation of thedisplayed modified parameters; utilizing the processor to automaticallydisplay a determined focal modified parameter on the user interface, andprompt a manual re-entry of the displayed focal modified parameter;receiving through the user interface the manual re-entry of thedisplayed focal modified parameter; utilizing the processor toautomatically determine whether the manual re-entry of the displayedfocal modified parameter matches the displayed focal modified parameter,and designate the displayed focal modified parameter as valid if themanual re-entry of the displayed focal modified parameter matches thedisplayed focal modified parameter, otherwise prompt for another manualre-entry of the displayed focal modified parameter or a change to theconfiguration file; and utilizing the processor to automatically writethe configuration file to the medical device once every determined focalmodified parameter has been designated valid.

One embodiment of a computer readable medium tangibly embodying aprogram of instructions executable by a computing device to performmethod steps includes reading a configuration file with one or moremodified parameters from memory, determining whether the configurationfile contains modified parameters that are focal, displaying themodified parameters, prompting an operator to confirm the displayedmodified parameters, receiving a confirmation of the displayed modifiedparameters, displaying a determined focal modified parameter, promptinga manual re-entry of the displayed focal modified parameter, receivingthe manual re-entry of the displayed focal modified parameter,determining whether the manual re-entry of the displayed focal modifiedparameter matches the displayed focal modified parameter, designatingthe displayed focal modified parameter as valid if the manual re-entryof the displayed focal modified parameter matches the displayed focalmodified parameter, otherwise prompting for another manual re-entry ofthe displayed focal modified parameter or a change to the configurationfile, and writing the configuration file to a medical device once everydetermined focal modified parameter has been designated valid.

One embodiment of a system for configuring a medical device includes acomputing device that includes a user interface, a processor and memory,and software stored in memory for execution by the computing device, thesoftware facilitating a workflow including the steps of reading aconfiguration file with one or more modified parameters from memory,determining whether the configuration file contains modified parametersthat are focal, displaying the modified parameters, prompting anoperator to confirm the displayed modified parameters, receiving aconfirmation of the displayed modified parameters, displaying adetermined focal modified parameter, prompting a manual re-entry of thedisplayed focal modified parameter, receiving the manual re-entry of thedisplayed focal modified parameter, determining whether the manualre-entry of the displayed focal modified parameter matches the displayedfocal modified parameter, designating the displayed focal modifiedparameter as valid if the manual re-entry of the displayed focalmodified parameter matches the displayed focal modified parameter,otherwise prompting for another manual re-entry of the displayed focalmodified parameter or a change to the configuration file, and writingthe configuration file to a medical device once every determined focalmodified parameter has been designated valid.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the teachings herein will be more apparent and betterunderstood by reference to the following description of embodimentstaken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a conceptual diagram of a computing device in communicationwith a medical device;

FIG. 2 is a perspective view of an insulin pump;

FIG. 3 is a block diagram of the internal components of the insulin pumpof FIG. 2;

FIG. 4 is a block diagram of an embodiment of a method and/or workflowof modifying configuration file parameters;

FIGS. 5-8 are screenshots relating to the modifying of a parameter of aconfiguration file;

FIGS. 9-11 are screenshots relating to the establishing of communicationbetween a medical device and a computing device;

FIG. 12 is a screenshot relating to the displaying of a modifiedparameter of a configuration file and the prompting of a confirmation ofthe modified parameter;

FIG. 13 is a screenshot relating to the displaying of a determined focalparameter and the prompting of a manual re-entry of the displayed focalmodified parameter;

FIG. 14 is a screenshot relating to the receiving of a manual re-entryof the displayed focal modified parameter; and

FIGS. 15-16 are screenshots relating to the writing of a configurationfile to a medical device.

DETAILED DESCRIPTION

Embodiments of methods, systems and computer readable media describedherein relate to setting and/or modifying focal parameters of aconfiguration file of a medical device. The embodiments of the teachingsdescribed below are not intended to be exhaustive or to limit theteachings to the precise forms disclosed in the following detaileddescription. Rather, the embodiments are chosen and described so thatothers skilled in the art may appreciate and understand the principlesand practices of the present teachings.

Accordingly, it should be understood that although the concepts beloware described as relating to insulin pumps and insulin pumpconfiguration software, such as the ACCU-CHEK® Insulin PumpConfiguration Software provided by Roche Diagnostics Corporation, theconcepts also relate to diabetes management software systems fortracking and analyzing health data, such as, for example, the ACCU-CHEK®360° product provided by Roche Diagnostics Corporation, as well as anyother medical device or medical device software that incorporates aconfiguration file (e.g., basic blood-glucose meters, advancedblood-glucose meters, etc.). The concepts also relate to hub devices andpass-through devices that communicate with and/or control one or moremedical devices. Moreover, the concepts described herein may also haveapplicability to apparatuses, methods, systems, and software in fieldsthat are unrelated to healthcare. Furthermore, it should be understoodthat references in this patent application to devices, pumps, meters,monitors, or related items are intended to encompass any currentlyexisting or later developed apparatus that includes some or all of thefeatures attributed to the detailed apparatus, including but not limitedto, the ACCU-CHEK® Active, ACCU-CHEK® Aviva, ACCU-CHEK® Compact,ACCU-CHEK® Compact Plus, ACCU-CHEK® Integra, ACCU-CHEK® Go, ACCU-CHEK®Performa, ACCU-CHEK® Spirit, ACCU-CHEK® D-Tron Plus, and ACCU-CHEK®Voicemate Plus, all provided by Roche Diagnostics Corporation ordivisions thereof.

An insulin pump (e.g., ACCU-CHEK® Spirit) is a fluid infusion device fordelivering insulin to people who suffer from diabetes. The pump, whichis worn by the user and eliminates the need for multiple daily insulininjections, closely imitates a normally functioning pancreas byreleasing hundreds of small doses of insulin each day into the bodythrough an infusion set to regulate blood glucose levels. The rate ofdelivery of these small doses (i.e., the basal rate) varies from user touser. Indeed, even for a particular user, the basal rate may varythroughout the day, and depends upon a variety of factors such as theuser's internal clock, metabolism, physical health, and level of stressand exercise. Insulin pumps may also deliver (either automatically orwhen activated by the user) bolus doses of insulin (in addition to thebasal rate) before meals or snacks to compensate for caloric intake.

As the amount and rate of insulin delivery (both basal and bolus) mustbe tailored to the individual needs of the user, modern pumps areprogrammable. Some pumps are capable of communicating with a separatecomputing device, and are compatible with software applications that maybe executed on the computing device. The software permits an operator,such as the user or a health care provider, to customize the settings ofthe various parameters that affect the operation of the pump. Theseparameters are encompassed in a configuration file that is executed bythe pump, and may include hourly basal rates, maximum hourly basalrates, maximum daily basal rates, bolus dose settings, communicationsettings, battery settings, and many others. For example, usingprogramming software on a computing device, a user may upload aconfiguration file from the their pump, modify the settings for certainparameters to change the operation of the pump, and save the modifiedconfiguration file to the pump. Alternatively, a health care providerresponsible for programming the pumps of multiple patients may select aninitial configuration file stored on a pump or computing device as astarting point for programming the patients' pumps. Many of theparameter settings of the initial configuration file (e.g., batterytype, language, etc.) may be suitable for all of the pumps to beprogrammed. Other settings (e.g., total daily basal rates, bolus dosesettings, etc.) may be unique to each patient's pump. After the healthcare provider selects the initial configuration file, he or she maychange only the settings needed to customize the pump's operation for anindividual patient, then save the customized configuration file to thatpatient's pump without having to define a setting for every pumpparameter.

Referring to the figures, FIG. 1 depicts an exemplary embodiment of acomputing device 12, some or all of the components of which may be usedin conjunction with the teachings of the present disclosure. Computingdevice 12, shown here in the form of a computer, generally includes auser interface 14 (including a video screen or monitor having screen 18and a keyboard 16), a processor 13 and memory 15, which may containand/or access the software 17 of the present disclosure and data 19 asis further described herein. Computing device 12 may also incorporate apointing device or mouse 20 connected to it by cable 22 (or wirelessly).In addition, while mouse 20 and keyboard 16 are illustrated, computingdevice 12 may also include any other input device such as a touchpad,joystick, touch screen, trackball, etc.

While described and depicted herein with specific reference to acomputer, certain concepts of the present disclosure may be utilized inconjunction with any type of computing device capable of operatingmedical device programming software, such as, for example, a medicalwebsite, a hub device, a stand-alone device (e.g., a blood-glucosemeter, a personal digital assistant), a pass-through device (e.g., ablood-glucose meter with pass-through capability) and/or a computingdevice incorporated on or within the medical device. Further, any typeof computing device may be used in conjunction with a hub device and/ora pass-through device in the communication with and/or control of one ormore medical devices. For example, in one embodiment, the computingdevice may be a computer, medical website and/or stand-alone device thatis utilized to communicate with a hub device, that in turn, controls oneor more configurable medical devices. In another embodiment, thecomputing device may be a computer, medical website and/or stand-alonedevice that is utilized to communicate with a blood-glucose meter withpass-through capability, that in turn, controls a configurable medicaldevice. In another embodiment, the computing device is the hub devicethat controls one or more configurable medical devices.

Memory 15 of computing device 12 may include a variety ofcomputer-readable media. Computer-readable media can be any availablemedia that can be accessed by computing device 12 and includes bothvolatile and non-volatile media, and removable and non-removable media.By way of example, and not limitation, computer-readable media maycomprise computer storage media and communication media. Storage mediaincludes, but is not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, Digital Versatile Disk (DVD) or other opticaldisk storage, magnetic cassettes, magnetic tape, magnetic disk storageor other magnetic storage devices, or any other medium which can be usedto store computer-readable instructions, software, data structures,program modules and other data and which can be accessed by computingdevice 12. Computer-readable media may be accessed directly or through anetwork such as the Internet.

Still referring to FIG. 1, computing device 12 is configured to provideinformation to, and receive information from, a medical device 24 (e.g.,an insulin pump or other configurable device). Again, while an insulinpump is specifically described herein as medical device 24, it should beunderstood that the teachings of the present disclosure may also applyto other medical devices that utilize configuration files, such as, forexample, “smart” insulin pens or other such devices known or hereafterdeveloped. Computing device 12 is shown coupled to communication mediaor dongle 26, in this case a modulated signal transceiver, accessible tocomputing device 12 by means of cable 28, and configured to transmit andreceive modulated signal 30 to establish logical communication withmedical device 24. In another exemplary embodiment, computing device 12and medical device 24 may include ports configured to establish aphysical connection. By way of example, and not limitation, dongle 26may include wired media such as a wired network or direct wiredconnection, and wireless media such as acoustic, RF, infrared,Bluetooth® and other wireless media. More specifically, dongle 26 asdepicted includes an infrared port for communication with a similarinfrared port for medical device 24.

Referring to FIG. 2, medical device 24 is depicted as an insulin pumpthat includes a display 32 for displaying information to an operator oruser, a menu button 34 for navigating though the various functionsprovided by medical device 24, a check button 36 for selecting options,an up key 38 and down key 40 for scrolling through options andcontrolling certain insulin delivery functions, a cartridge receptacle42 for storing an insulin cartridge 44, a battery 46 (shown partiallyinserted), a battery cap 48 (shown unsecured to medical device 24), anadapter 50 for physically coupling cartridge 44 to an infusion set 52,and a communication port 53 for sending information to, or receivinginformation from, computing device 12 through dongle 26.

FIG. 3 provides a block diagram representation of internal components ofmedical device 24. As shown, medical device 24 may include a processor54 coupled to a display interface 56, which is coupled to display 32.Processor 54 may also be coupled to a keypad interface 58 which iscoupled to keys 34, 36, 38, 40, and a pump actuator interface 62 whichis coupled to an actuator 64 suitable for delivering insulin doses(medical infusion pumps other than insulin pumps will deliver doses ofother medicament). Processor 54 is further coupled to a memory device 66that stores application programs and data, including the configurationfiles described herein. Memory device 66 may be constructed of anycombination of volatile and/or nonvolatile memory suitable for aparticular embodiment. Processor 54 may also be coupled to an alertmechanism 68, that, in various embodiments is a buzzer, a vibrator, alight emitting diode, or the like, suitable for providing audible,tactile, or visual alerts to an insulin pump user. Finally, processor 54may be coupled to a timer 60, which is capable of maintaining a currenttime, including time of day and day of the week.

In the context of the above-detailed computing device 12 and medicaldevice 24, embodiments of the methods, systems and computer readablemedia of the present teachings relate to the utilization of thecomputing device in adjusting the parameters, in particular the focalparameters, of a configuration file utilized by the medical device. Theterm “focal parameters” may be defined broadly or narrowly, depending onthe desired application of medical device 24. For example, in anapplication where medical device 24 is an insulin pump, the focalparameters may include parameters relating to insulin dosage rates, suchas, for example, the parameters of total daily basal amount and bolusdoses (e.g., maximum dose and standard increment). However, the focalparameters may include any other desired parameter of a configurationfile, and are therefore not limited to the above-detailed exemplaryparameters. Further, in embodiments of the methods, systems and computerreadable media that employ medical device 24 that is not an insulinpump, focal parameters may include any parameter(s) designated as focal.

Referring to FIG. 4, a block diagram representation of an embodiment ofa method or workflow (executable by computing device 12) that modifiesparameters of a configuration file of a medical device is illustrated.The depicted embodiment of method and/or workflow 100 includes a step102 for the initial setting, adjusting or modifying of one or moreparameters of a configuration file. Any parameter(s) that is encompassedin a configuration file may be initially set or modified in this step.In embodiments where the configuration file relates to an insulin pump,examples of such parameters may include hourly basal rates, maximumhourly basal rates, maximum daily basal rates, bolus dose settings,communication settings, battery settings, language settings and manyothers. After one or more parameters of the configuration file are setor modified, the configuration file may then be received in memory 15 ofcomputing device 12.

Another step 104 provides that communication is established betweenmedical device 24 and computing device 12. As detailed above, thecommunication may be established through wires or wirelessly, throughdongle 26 or otherwise. However, in embodiments that may have computingdevice 12 incorporated within medical device 24, communication betweenthe two may have already been established, on a temporary or permanentbasis. In other embodiments, the communication between medical device 24and computing device 12 may further utilize a hub device or apass-through device. In embodiments that include a hub device, computingdevice 12 communicates with the hub device and the hub device sends thecommunication to one or more medical devices 24. In embodiments thatinclude a pass-through device, computing equipment 12 communicates withthe pass-through device, and the pass-through device then passes thecommunication along to one or more medical devices 24. Also, as detailedabove, computing device 12 may comprise the hub device.

In some embodiments of method and/or workflow 100, step 102 may involvea user uploading a configuration file from the user's medical device andmodifying the settings for certain parameters. In such an embodiment,communication would have to have already been established betweenmedical device 24 and computing device 12 to allow for the uploading ofthe configuration file from the medical device to the computing device.Accordingly, in such embodiments, step 104 may precede step 102.However, in other embodiments, step 102 may involve a health careprovider selecting an initial configuration file stored on computingdevice 12 as a starting point. In such embodiments, steps 102 and 104may be ordered as illustrated in FIG. 4. Therefore, the ordering ofsteps 102 and 104, as well as the ordering of any other steps in methodand/or workflow 100 described herein, should not be restricted to theillustrated arrangement of the embodiment of FIG. 4.

Once the parameters of the configuration file are set and/or modified,and communication is established between computing device 12 and themedical device 24, step 106 may be automatically executed by processor13 of the computing device. In this step, processor 13 utilizes logic todetermine if any of the one or more modified parameters of theconfiguration file are focal. As detailed above, focal parameters may bedefined on an application-by-application basis. In one embodiment wheremedical device 24 is an insulin pump, non-limiting examples of focalparameters may be total daily basal amount and parameters regardingbolus doses (e.g., maximum doses and standard increments).

If processor 13 determines that the configuration file with one or moremodified parameters does not contain a focal modified parameter, methodand/or workflow 100 proceeds to step 108. In that step, processor 13displays the modified parameters of the configuration file on userinterface 14. In some embodiments, user interface 14 may display onlythe modified parameter(s). However, in other embodiments, user interface14 may display the entire configuration file with the one or moremodified parameter(s) highlighted. Additionally in step 108, the displaymay prompt a user to confirm the modified parameters of theconfiguration file. In step 110, a user may then confirm the displayedmodified parameters of the configuration file through user interface 14of computing device 12. In step 112, processor 13 writes theconfiguration file to medical device 24.

Referring back to step 106, if processor 13 determines that theconfiguration file contains one or more modified parameters that arefocal, method and/or workflow 100 proceeds to step 114. In that step,processor 13 displays the modified parameters of the configuration fileon user interface 14. In some embodiments, user interface 14 may displayonly the modified parameter(s). However, in other embodiments, such asthe illustrated embodiment, user interface 14 may display the entireconfiguration file with the one or more modified parameter(s)highlighted. Additionally in step 114, the display may prompt a user toconfirm the modified parameters of the configuration file. In step 116,a user may then confirm the displayed modified parameters of theconfiguration file through user interface 14 of computing device 12.

Once a user confirms the displayed modified parameters of theconfiguration file, method and/or workflow 100 moves on to step 118. Inthat step, a focal modified parameter is displayed on user interface 14,along with a prompting to have a user manually re-enter the displayedfocal parameter. A user may then manually re-enter the focal modifiedparameter through user interface 14 of computing device 12. In step 120,processor 13 may automatically determine whether the manual re-entry ofthe displayed focal modified parameter matches the displayed focalmodified parameter. If the manual re-entry of the displayed focalmodified parameter matches the displayed focal modified parameter,processor 13 designates the displayed focal parameter as valid.Conversely, if the manual re-entry of the displayed focal modifiedparameter does not match the displayed focal modified parameter,processor 13 may automatically prompt for another manual re-entry of thedisplayed focal modified parameter or a change to the configurationfile. Moreover, if the configuration file includes more than one focalmodified parameter, steps 118 and 120 may be repeated for each focalmodified parameter. Once all of the focal modified parameters have bedesignated as valid, the method may move to step 122. In step 122,processor 13 writes the configuration file to medical device 24.

In addition, FIGS. 5-16 provide screenshots from user interface 14 ofcomputing device 12 during the execution of a particular embodiment ofmethod and/or workflow 100 that is specific to adjusting the bolus dosestandard increment parameter of a configuration file for an insulinpump. In this specific embodiment, the only modified parameter of theconfiguration file is the bolus dose standard increment, and thatparameter is defined as focal. Accordingly, steps 102, 104, 106 and114-122 are performed for method and/or workflow 100 illustrated in FIG.4.

FIG. 5 depicts a parameter modification screen 200 of user interface 14that is displayed when a user utilizes computing device 12 to modify theparameters of a configuration file. Screen 200 generally includes anavigation menu 202 and an active window 204. Navigation menu 202includes a Save Settings button 205 and a Basal Rates and Bolus button206 with an indicator 208 denoting the existence of a dropdown menuassociated with button 206. The content displayed in active window 204changes depending on the operation being performed by software 17 (whichcontains and/or has access to a computer readable medium tangiblyembodying method and/or workflow 100). In the screenshot of FIG. 5,indicator 208 has been activated, and three sub-options under button 206have been presented. Of those presented options, a Bolus button 210 hasbeen activated. Accordingly, the activation of button 210 requiressoftware 17 to control active window 204 to display four boxes relatingto the modification of bolus parameters. One of those four boxes is“Quick” Standard Bolus box 212. Box 212 includes a Maximum Dose dataentry box 214 with an indicator 216 denoting the existence of a dropdownmenu associated with button 214, and a Standard Increment data entry box218 with an indicator 220 denoting the existence of a dropdown menuassociated with button 218. As shown in FIG. 6, when indicator 220 isactivated, five sub-options under data entry box 218 are presented. Thesub-option of 1 has been highlighted for selection. In FIG. 7, thesub-option for 1 has been selected, and is displayed in data entry box218. The message 222 displayed along the bottom of the screenshot inFIG. 7 indicates at least one parameter of the configuration file hasbeen modified.

The screenshot of FIG. 8 illustrates that button 205 has been activated,causing software 17 to control a pop-up Save Settings dialog box 224 tobe displayed over active window 204. On dialog box 224, the Save to anInsulin Pump button 226 has been selected. As illustrated in FIG. 9,after button 226 is activated, software 17 controls a pop-up Save to anInsulin Pump—Prepare Insulin Pump dialog box 227 to be displayed overactive window 204. At this point, a user would line up medical device 24with dongle 26 connected to computing device 12 to establishcommunication between the medical device and the computing device. Thescreenshot of FIG. 10 illustrates a Save to an InsulinPump—Communication Status dialog box 228 displayed over active window204, in which a message “Searching for insulin pump . . . ” 230 and amagnifying glass icon 232 are displayed. At this point, computing device12 is attempting to establish communication with medical device 24. Asillustrated in the screenshot of FIG. 11, once communication isestablished, the message of dialog box 228 changes to “Communicatingwith insulin pump . . . ” 234 and the icon changes to a computer/arrowicon 236. At this point, communication between the computing device 12and medical device 24 has been established.

Once communication is established, processor 13 automatically reads themodified parameter of the configuration file (“Quick” StandardBolus—Standard Increment parameter changed from 2 units to 1 unit), andmakes the determination that the modified parameter is focal (becausesuch a modification was previously defined as focal). Accordingly,referring to FIG. 4, the method and/or workflow goes from step 106 tostep 114. As illustrated in the screenshot of FIG. 12, software 17controls a Save to an Insulin Pump—Confirm Changes dialog box 238 to bedisplayed over active window 204. The one modified parameter of theconfiguration file (“Quick” Standard Bolus, Standard Increment) isdisplayed in dialog box 238 with the modification highlighted. At thispoint, if a user agrees with the parameter modification, a user thenchecks box 240 for “Confirm 1 Change(s)” and activates the NEXT button242. When NEXT button 242 is activated, as illustrated in FIG. 13,processor 13 automatically displays a Confirm Change to Focal Settingdialog box 244 over dialog box 238, which is displayed over activewindow 204. Dialog box 244 includes identification of the particularfocal parameter being modified, the current parameter setting 248 andthe modified parameter setting 250. Dialog box 244 also includes a dataentry window 252 for manually re-entering the focal modified parameter.At this time, a user would utilize user interface 14 of computing device12 to re-enter the focal modified parameter. The screenshot of FIG. 14illustrates the focal modified parameter manually re-entered into dataentry window 252. Once the modified parameter has been manuallyre-entered, the CONFIRM button 254 is activated.

With the focal modified parameter manually re-entered, processor 13automatically determines if the re-entry of the displayed focal modifiedparameter matches the displayed focal modified parameter. The two valuesmatch, and processor 13 designates the displayed focal parameter asvalid. If the configuration file contained more than one focal modifiedparameter, the screenshots/steps of FIGS. 13 and 14 would be repeatedfor each additional focal modified parameter. However, because theconfiguration file only contained one focal modified parameter, everyfocal modified parameter has been designated valid. Accordingly,processor 13 automatically controls computing device 12 to communicatewith medical device 24 in order to write the configuration file to themedical device. This process is illustrated in FIG. 15, wherein the Saveto an Insulin Pump—Communication Status dialog box 256 is shown. Asillustrated in FIG. 16, when the new configuration file is written tomedical device 24, the Save to an Insulin Pump—Finished dialog box 258is displayed.

While an exemplary embodiment incorporating the principles of thepresent teachings has been disclosed hereinabove, the present teachingsare not limited to the disclosed embodiments. Accordingly, thisapplication is intended to cover any variations, uses or adaptations ofthe disclosed general principles. Further, this application is intendedto cover such departures from the present disclosure as come withinknown or customary practice in the art to which this applicationpertains and which fall within the limits of the appended claims.

What is claimed is:
 1. A method of configuring an insulin pump throughutilization of a glucose meter that includes a user interface, aprocessor and memory, the method comprising: receiving in the glucosemeter memory a configuration file with one or more modified parameters,wherein the modified parameters includes hourly basal rates, maximumhourly basal rates, maximum daily basal rates, bolus dose settings,communication settings, battery settings, and language setting;establishing communication between the insulin pump and the glucosemeter; utilizing the glucose meter processor to automatically: read theconfiguration file from memory, determine whether the configuration filecontains modified parameters and whether any of the modified parametersdetermined to be contained in the configuration file are focal, whereinthe modified parameters are focal if the modified parameters relate toinsulin dosage rates which include any of the modified parameter to thehourly basal rates, the maximum hourly basal rates, the maximum dailybasal rates, and the bolus dose settings, display the entireconfiguration file with the modified parameters highlighted on theglucose meter user interface, prompt a confirmation of the displayed andhighlighted modified parameters only once when the displayed andhighlighted modified parameters are not focal which include any of themodified parameters to the communication settings, the battery settings,and the language setting; receiving through the glucose meter userinterface the confirmation of the displayed and highlighted modifiedparameters that are not focal; utilizing the glucose meter processor toautomatically: prompt a manual re-entry of a displayed and highlightedfocal modified parameter a second time when the displayed andhighlighted modified parameter is focal; receiving through the glucosemeter user interface the manual re-entry of the displayed andhighlighted focal modified parameter that is focal; utilizing theglucose meter processor to automatically: determine whether the manualre-entry of the displayed and highlighted focal modified parametermatches the displayed and highlighted focal modified parameter, anddesignate the displayed and highlighted focal modified parameter asvalid if the manual re-entry of the displayed and highlighted focalmodified parameter matches the displayed and highlighted focal modifiedparameter, otherwise prompt for another manual re-entry of the displayedand highlighted focal modified parameter or a change to theconfiguration file; and utilizing the glucose meter processor toautomatically: store the configuration file in memory of the insulinpump once every determined focal modified parameter has been designatedvalid.
 2. A non-transitory computer readable medium tangibly embodying aprogram of instructions executable by a processor of a computing devicethat is disposed on or within a glucose meter to cause the processor toperform the method steps of claim
 1. 3. A system for configuring amedical device including: a computing device that includes a userinterface, a processor and memory, wherein the computing device isdisposed on or within a glucose meter; and software stored in memory forexecution by the computing device, the software facilitating a workflowincluding the method steps of claim 1.